Inside Macintosh: Programming With JManager /

Chapter 1 - Using JManager

Changes in JManager 2.0

JManager 2.0, as included with Mac OS Runtime for Java 2.0, extends or improves the functionality of previous versions. The JManager 2.0 library still supports the older functions; you are not required to update older code for MRJ 2.0 compatibility. However, if you build your application using JManager 2.0 headers, you can no longer use the older 1.0 functions.

The major changes for JManager 2.0 are as follows:

• The new JMTextRef object used to encapsulate strings. This object allows you to pass Unicode strings as well as Mac OS strings. All strings passed by JManager functions are now passed as text objects.
• New flags used with the JMOpenSession function, to allow use of the Just In Time Compiler (JITC), InternetConfig, and the application heap.
• Abstract Window Toolkit (AWT) contexts no longer have a suspended state.
• Security options are now bound to individual applets, not to a session.
• Graphics ports (grafPort) are now bound directly to frames, rather than accessed through a callback.
• The applet viewer callback MyShowDocument now specifies the name of the frame in which the document is to be shown.
• New callbacks for handling calls to java.lang.System.exit,URL password authentication, and low-memory conditions.
• Java bindings for most JManager functions. These allow your Java application to call JManager methods. See Chapter 3, "JManager Java Class Reference," for listings of JManager Java classes and interfaces.
• Use of the Java Native Interface (JNI), rather than the Java Runtime Interface (JRI) to access Java methods. If desired, however, you can still access methods using the Java Runtime Interface.

For a listing of changes to individual functions, see Appendix A. You can use this listing to determine quickly which function calls or callbacks you may need to update.